Option available for the configuration:
- pic: if True, build the code as position-independent
- hashed: perform the hash of the library and check it at runtime
- type: indicate how crypto is build.
    static (default): using cc_library. Self-check is not supported in
        this case.
    binary_blob: using opentitan_binary_blob custom rule. The cryptolib is
        provide as a binary blob and then integrated in a static library as
        an array of bytes.
    relocatable: using opentitan_relocatable custom rule. The cryptolib is
        provided as a relocatable library.

Update the compilation flag if pic option is selected to build the
code as position-independent.

Build the library in different ways depending on the type option. (Only
dev supported for the moment).

- dev: build the cryptolib as a static library (as previously), the self-integrity
    check cannot be performed in that case. Both pic
    (position-independent code) or pdc (position-dependent code) is supported.
    by default pdc is chosen.
- fips_all: build the the cryptolib using a binary blob library, the code is
    position-independent, hash self-integrity check is performed

With thanks to Elieva Pignat <elievap@google.com>

Signed-off-by: Siemen Dhooghe <sdhooghe@google.com>

Generate files for the binary blob compilation. It supports both
position-dependent and position-independent code. This information is
provided as an argument.
- jump_table.c/.h: array that contain the function names that are
    part of the public interface. To generate those files it takes in
    inputs the public header files and a configuration that contains the
    name of the function names that are part of the library. It keeps
    the functions that are in the intersection of the headers and the
    configuration.
    It generates also an enumeration based on the name of the function
    A metadata that contain a version and a magic number
- linker_script.ld: generate a linker script to create the binary blob
    This file is generated because the address at which the blob is
    placed can change and be provided in argument. In case of PIC,
    the address should be 0.
- lib_parser.c: Provide a wrapper for the public interface. Parse the
  blob to find the function address. In case of PIC, this address is
  increment by the blob address offset, to reflect the relocation of the
  blob in the memory.

With thanks to Elieva Pignat <elievap@google.com>

Signed-off-by: Siemen Dhooghe <sdhooghe@google.com>

Add a custom compilation rule in bazel that compiles crypto into a
binary blob and include this blob into libotcrypto. This library can then
be used for an application and allows to perform a self-integrity check
on the binary blob.

Try it out via ./bazelisk build //sw/device/lib/crypto:cryptolib
--config=fips_all

Also added two rules to get the elf or dis of the cryptolib in this
mode.

With thanks to Elieva Pignat <elievap@google.com>

Signed-off-by: Siemen Dhooghe <sdhooghe@google.com>